Windows Server Deployment SOP
Purpose
Standardize licensed, hardened and recoverable Windows Server deployment.
Decision Summary
Mandatory CSI deployment control for applicable work; client-specific implementation requires approved scope and change authorization.
Use Cases
Active Directory, file/print, RDS, application, database, backup and infrastructure servers.
Field Notes
Do not deploy evaluation editions, unlicensed CAL/RDS use, unsupported Windows versions, direct internet RDP, shared Domain Admin accounts or BitLocker without escrowed keys.
Hardware Requirements
Supported hardware/VM, TPM where required, adequate licensed CPU/RAM/storage, UPS for physical server, backup repository and valid Microsoft licensing.
Backup Strategy
Preserve configuration, credentials references, certificates/keys, application data and deployment documentation according to the workload-specific RPO/RTO.
Recovery Strategy
Maintain a documented rollback and tested restoration path before production change; validate service, data, access and monitoring after recovery.
Secure Boot Notes
Enable UEFI Secure Boot and TPM when supported. Record BitLocker recovery keys outside the server before enabling encryption.
Version History
v1.0 created 2026-08-04 as the baseline CSI deployment and validation procedure.
Technology Register Metadata
- CSI Classification: Production Ready
- CSI Tech ID: 135
- Category: Field SOPs
- Client Approved: No
- Commercial Use: Allowed
- Current Version: 1.0 — 2026-08-04
- Deployment: Cloud, Docker, Hybrid, Native, VM
- Docker Support: Not Applicable
- Evidence Complete: Yes
- Last Updated: August 8, 2026 5:09 PM
- Last Verified: August 4, 2026
- Licence: CSI Internal SOP — not software; underlying products retain their own licence terms.
- Lifecycle Status: Done
- OS Support: Linux, Web, Windows
- Offline Support: Full
- Risk Flag: Caution
- Ventoy Compatibility: Not Applicable
Migration Record
Imported deterministically from the CSI Technology Register.
Source classifications, approval state, risk state, version information and testing status have been preserved. No additional approval or validation has been inferred during migration.
Cyber Space Infocom
Making Technology Work for You